Interconnect distributed virtual memory (DVM) message preemptive responding

ABSTRACT

Aspects include computing devices, apparatus, and methods for accelerating distributive virtual memory (DVM) message processing in a computing device. DVM message interceptors may be positioned in various locations within a DVM network of a computing device so that DVM messages may be intercepted before reaching certain DVM destinations. A DVM message interceptor may receive a broadcast DVM message from first DVM source. The DVM message interceptor may determine whether a preemptive DVM message response should be returned to the DVM source on behalf of the DVM destination. When certain criteria are met, the DVM message interceptor may generate a preemptive DVM message response to the broadcast DVM message, and send the preemptive DVM message response to the DVM source.

BACKGROUND

In a distributed virtual memory (DVM) system, such as used in AdvancedRISC Machines (ARM) processors, DVM messages from a DVM source (e.g., acentral processor unit (CPU)) are broadcast to all other DVM sources andto all DVM destinations (e.g., a system memory management unit (SMMU)).The DVM messages are distributed by a coherent interconnect and/or a DVMnetwork, and such components gather responses from the DVM sources anddestinations, merge the responses into a single response, and return asingle response to the sending DVM source. Thus, the total response timefor a DVM message is controlled by the slowest response.

SUMMARY

The methods and apparatuses of various aspects provide circuits andmethods for distributive virtual memory (DVM) preemptive responding on acomputing device. An aspect method may include receiving a DVM messagebroadcast from a first DVM source in a DVM message interceptor prior todelivery of the DVM message to a DVM destination, determining based on acontent of the DVM message whether a preemptive DVM message responseshould be sent by the DVM message interceptor, generating the preemptiveDVM message in response to determining that a preemptive DVM messageresponse should be sent by the DVM message interceptor, and sending thepreemptive DVM message response from the DVM message interceptor to thefirst DVM source.

Various aspects may include enabling the broadcast DVM message to reachthe DVM destination in response to determining that a preemptive DVMmessage response should not be sent by the DVM message interceptor.

In some aspects, the DVM destination is a memory management unit and theDVM message interceptor is positioned within a DVM system to interceptthe DVM message before the DVM message reaches the memory managementunit.

Various aspects may include preventing the DVM destination fromreceiving the broadcast DVM message in response to determining that apreemptive DVM message response should be sent by the DVM messageinterceptor.

In some aspects, determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent by the DVMmessage interceptor may include comparing data obtained from thebroadcast DVM message with corresponding data in at least one of awhite-list and a black-list, and determining whether a preemptive DVMmessage response should be sent by the DVM message interceptor basedupon the comparison.

In some aspects, determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent by the DVMmessage interceptor may include applying a mask to data obtained fromthe broadcast DVM message.

In some aspects, determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent by the DVMmessage interceptor may include comparing data obtained from thebroadcast DVM message with a criterion comprising at least one of avirtual memory identifier, a shared process context, a DVM operation, amemory translation stage identifier, and an execution level identifier.

Various aspects may include a distributive virtual memory (DVM) messageinterceptor configured for DVM preemptive responding. The DVM messageinterceptor may include a DVM communication interface, a preemptionidentifier, and a DVM message response generator respectively configuredto perform operations of one or more of the embodiment methodssummarized above.

Various aspects may include a distributive virtual memory (DVM) messageinterceptor configured for DVM preemptive responding having means forperforming functions of one or more of the embodiment methods summarizedabove.

Various embodiments may include a non-transitory processor-readablestorage medium having stored thereon processor-executable instructionsconfigured to cause a processor of a distributive virtual memory (DVM)message interceptor to perform operations of one or more of theembodiment methods summarized above.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate example aspects of variousaspects, and together with the general description given above and thedetailed description given below, serve to explain the features of theclaims.

FIG. 1 is a component block diagram illustrating a computing devicesuitable for implementing an aspect.

FIG. 2 is a component block diagram illustrating an example multi-coreprocessor suitable for implementing an aspect.

FIG. 3 is a component block illustrating an example distributed virtualmemory message interceptor suitable for implementing an aspect.

FIG. 4 is a component block diagram illustrating a distributed virtualmemory system with distributed virtual memory message interceptorssuitable for implementing an aspect.

FIGS. 5A and 5B are signaling diagrams illustrating an example ofdistributed virtual memory preemptive responding according to an aspect.

FIG. 6 is a process flow diagram illustrating a method for implementingdistributed virtual memory preemptive responding according to an aspect.

FIG. 7 is a component block diagram illustrating an example mobilecomputing device suitable for use with the various aspects.

FIG. 8 is component block diagram illustrating an example mobilecomputing device suitable for use with the various aspects.

FIG. 9 is component block diagram illustrating an example serversuitable for use with the various aspects.

DETAILED DESCRIPTION

The various aspects will be described in detail with reference to theaccompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.References made to particular examples and aspects are for illustrativepurposes, and are not intended to limit the scope of the claims.

The terms “computing device” and “mobile computing device” are usedinterchangeably herein to refer to any one or all of cellulartelephones, smartphones, personal or mobile multi-media players,personal data assistants (PDA's), laptop computers, tablet computers,convertible laptops/tablets (2-in-1 computers), smartbooks, ultrabooks,netbooks, palm-top computers, wireless electronic mail receivers,multimedia Internet enabled cellular telephones, mobile gaming consoles,wireless gaming controllers, and similar personal electronic devicesthat include a memory, and a programmable processor. The term “computingdevice” may further refer to stationary computing devices includingpersonal computers, desktop computers, all-in-one computers,workstations, super computers, mainframe computers, embedded computers,servers, home theater computers, and game consoles.

Various aspects include methods, and systems and devices forimplementing one or multiple DVM message interceptors in the coherentinterconnect or in an additional DVM network to shorten the averageresponse time by providing a prompt response to DVM messages for DVMdestinations that will not process or implement the particular type ofDVM messages. Intercepting and responding on behalf of DVM destinationsthat will not process/implement certain DVM messages eliminates the lagin DVM signaling that would otherwise be incurred waiting for some DVMdestinations to acknowledge irrelevant DVM messages.

In DVM systems, DVM sources and coherent interconnects typically runfive to ten times faster than DVM networks and DVM destinations. The DVMmessages broadcast by the DVM sources include messages for DVMoperations. Such operations include translation lookaside buffer (TLB)invalidate, synchronization, instruction cache invalidate, branchpredictor invalidate, and hint operations. Broadcasting the DVM messagessends the DVM messages to all DVM sources and destinations. However,broadcasting a DVM message to DVM sources and DVM destinations that arenot intended to implement the DVM operation or that do not implementsome of the DVM operation causes the system to wait for a response fromthose sources/destinations even though the DVM message is not relevantto those DVM sources/destination. Thus, broadcasting all DVM messages toall DVM sources/destinations creates situations in which time must bespent waiting for responses from unintended recipients of the DVMmessages.

In various aspects, preemptively responding to DVM messages on behalf ofDVM destinations for which the DVM messages are irrelevant through theuse of DVM message interceptors improves the performance of DVM systemsby reducing response times and/or power consumption. Such DVM messageinterceptors may be implemented along transmission paths andcommunication links in the coherent interconnect and/or the DVM networksat locations in the networks that enable DVM messages to be interceptedand acknowledged in behalf of downstream DVM destinations. The DVMmessage interceptors may generate an appropriate response upon matchinga received DVM message to a preemptive response criterion. The DVMmessage interceptors may return the response to the associated coherentinterconnect or DVM network for merging and/or returning to the sourceof the DVM message broadcast. To restate simply, the DVM messageinterceptors may terminate and respond to DVM messages before themessages reach a source or destination for which the message is notintended or of no consequence (i.e., irrelevant).

The DVM message interceptors may be circuits implementing variousidentification techniques and criteria that are positioned in variouslocations within a DVM system. Any number of DVM message interceptorsmay be used in a processor, system on chip (SoC) or computing device,and each DVM message interceptor may be configured to implement one ormore identification techniques and criteria. The DVM messageinterceptors may be at placed on any transmission path downstream of apoint of serialization in the DVM system. The DVM message interceptorsmay be software programmable or fixed configuration. Methods andcriteria used to intercept DVM messages may trade off accuracy andperformance. For example, to provide better accuracy in identifyingirrelevant DVM messages at the expense of slower response times,white-list/black-list identification of DVM messages to be interceptedmay be implemented in look-up tables that are accessed by a DVM messageinterceptor. As another example, mask/match structure identification maybe used by DVM message interceptors to improve performance in terms ofreaction time and/or power usage at the expense of limiting flexibilityin terms of updates and/or the types of DVM messages that areintercepted.

The DVM message interceptors may implement any of a number of differenttypes of DVM message identification/recognition as described herein.

The DVM message interceptors intercept broadcast DVM messages, and readdestination and/or aspect data of the DVM messages in order to determinewhether the data triggers preemption identification of the DVM messages.The DVM message interceptors may preemptively respond to those receivedDVM messages for which the destination and/or aspect data triggerspreemption. In other words, in response to triggering preemptionidentification, the DVM message interceptors may generate an appropriateresponse to the DVM message (e.g., an acknowledgement of receipt by thecorresponding DVM destination) and return the response to an upstreamDVM interceptor associated with the DVM message interceptor. In someaspects, intercepted DVM messages may be terminated (i.e., not forwardedon to the DVM destination), but in some aspects intercepted DVM messagesmay be permitted to propagate to the DVM destination.

FIG. 1 illustrates a computing device 10 suitable for use with thevarious aspects. The computing device 10 may include a system-on-chip(SoC) 12 with a processor 14, a memory 16, a communication interface 18,and a storage memory interface 20. The computing device may furtherinclude a communication component 22 such as a wired or wireless modem,a storage memory 24, an antenna 26 for establishing a wirelesscommunication link. The processor 14 may include any of a variety ofhardware cores, for example a number of processor cores.

The term “system-on-chip” (SoC) is used herein to refer to a set ofinterconnected electronic circuits typically, but not exclusively,including a hardware core, a memory, and a communication interface. Ahardware core may include a variety of different types of processors,such as a general purpose processor, a central processing unit (CPU), adigital signal processor (DSP), a graphics processing unit (GPU), anaccelerated processing unit (APU), an auxiliary processor, a single-coreprocessor, and a multi-core processor. A hardware core may furtherembody other hardware and hardware combinations, such as a fieldprogrammable gate array (FPGA), an application-specific integratedcircuit (ASIC), other programmable logic device, discrete gate logic,transistor logic, performance monitoring hardware, watchdog hardware,and time references. Integrated circuits may be configured such that thecomponents of the integrated circuit reside on a single piece ofsemiconductor material, such as silicon.

An SoC 12 may include one or more processors 14. The computing device 10may include more than one SoCs 12, thereby increasing the number ofprocessors 14 and processor cores. The computing device 10 may alsoinclude processors 14 that are not associated with an SoC 12. Individualprocessors 14 may be multi-core processors as described below withreference to FIG. 2. The processors 14 may each be configured forspecific purposes that may be the same as or different from otherprocessors 14 of the computing device 10. One or more of the processors14 and processor cores of the same or different configurations may begrouped together. A group of processors 14 or processor cores may bereferred to as a multi-processor cluster.

The memory 16 of the SoC 12 may be a volatile or non-volatile memoryconfigured for storing data and processor-executable code for access bythe processor 14. The computing device 10 and/or SoC 12 may include oneor more memories 16 configured for various purposes. One or morememories 16 may include volatile memories such as random access memory(RAM) or main memory, or cache memory. These memories 16 may beconfigured to temporarily hold a limited amount of data received from adata sensor or subsystem, data and/or processor-executable codeinstructions that are requested from non-volatile memory, loaded to thememories 16 from non-volatile memory in anticipation of future accessbased on a variety of factors, and/or intermediary processing dataand/or processor-executable code instructions produced by the processor14 and temporarily stored for future quick access without being storedin non-volatile memory.

The memory 16 may be configured to store data and processor-executablecode, at least temporarily, that is loaded to the memory 16 from anothermemory device, such as another memory 16 or storage memory 24, foraccess by one or more of the processors 14. The data orprocessor-executable code loaded to the memory 16 may be loaded inresponse to execution of a function by the processor 14. Loading thedata or processor-executable code to the memory 16 in response toexecution of a function may result from a memory access request to thememory 16 that is unsuccessful, or a miss, because the requested data orprocessor-executable code is not located in the memory 16. In responseto a miss, a memory access request to another memory 16 or storagememory 24 may be made to load the requested data or processor-executablecode from the other memory 16 or storage memory 24 to the memory device16. Loading the data or processor-executable code to the memory 16 inresponse to execution of a function may result from a memory accessrequest to another memory 16 or storage memory 24, and the data orprocessor-executable code may be loaded to the memory 16 for lateraccess.

The storage memory interface 20 and the storage memory 24 may work inunison to allow the computing device 10 to store data andprocessor-executable code on a non-volatile storage medium. The storagememory 24 may be configured much like an aspect of the memory 16 inwhich the storage memory 24 may store the data or processor-executablecode for access by one or more of the processors 14. The storage memory24, being non-volatile, may retain the information after the power ofthe computing device 10 has been shut off. When the power is turned backon and the computing device 10 reboots, the information stored on thestorage memory 24 may be available to the computing device 10. Thestorage memory interface 20 may control access to the storage memory 24and allow the processor 14 to read data from and write data to thestorage memory 24.

Some or all of the components of the computing device 10 may bedifferently arranged and/or combined while still serving the necessaryfunctions. Moreover, the computing device 10 may not be limited to oneof each of the components, and multiple instances of each component maybe included in various configurations of the computing device 10.

FIG. 2 illustrates a multi-core processor 14 suitable for implementingan aspect. The multi-core processor 14 may have a plurality ofhomogeneous or heterogeneous processor cores 200, 201, 202, 203. Theprocessor cores 200, 201, 202, 203 may be homogeneous in that, theprocessor cores 200, 201, 202, 203 of a single processor 14 may beconfigured for the same purpose and have the same or similar performancecharacteristics. For example, the processor 14 may be a general purposeprocessor, and the processor cores 200, 201, 202, 203 may be homogeneousgeneral purpose processor cores. Alternatively, the processor 14 may bea graphics processing unit or a digital signal processor, and theprocessor cores 200, 201, 202, 203 may be homogeneous graphics processorcores or digital signal processor cores, respectively. For ease ofreference, the terms “processor” and “processor core” may be usedinterchangeably herein.

The processor cores 200, 201, 202, 203 may be heterogeneous in that, theprocessor cores 200, 201, 202, 203 of a single processor 14 may beconfigured for different purposes and/or have different performancecharacteristics. The heterogeneity of such heterogeneous processor coresmay include different instruction set architecture, pipelines, operatingfrequencies, etc. An example of such heterogeneous processor cores mayinclude what are known as “big.LITTLE” architectures in which slower,low-power processor cores may be coupled with more powerful andpower-hungry processor cores. In similar aspects, the SoC 12 may includea number of homogeneous or heterogeneous processors 14.

In the example illustrated in FIG. 2, the multi-core processor 14includes four processor cores 200, 201, 202, 203 (i.e., processor core0, processor core 1, processor core 2, and processor core 3). For easeof explanation, the examples herein may refer to the four processorcores 200, 201, 202, 203 illustrated in FIG. 2. However, the fourprocessor cores 200, 201, 202, 203 illustrated in FIG. 2 and describedherein are merely provided as an example and in no way are meant tolimit the various aspects to a four-core processor system. The computingdevice 10, the SoC 12, or the multi-core processor 14 may individuallyor in combination include fewer or more than the four processor cores200, 201, 202, 203 illustrated and described herein.

FIG. 3 illustrates a non-limiting example of a DVM message interceptor300 according to some aspects. The DVM message interceptor 300 may beimplemented as a standalone hardware component (e.g., a circuit) of acomputing device or as an integrated hardware component of an SoC of thecomputing device. The DVM message interceptor 300 may include a DVMcommunication interface 302, a preemption identifier 304, a DVM messagetracker 306, and a DVM message response generator 308. The components ofthe DVM message interceptor 300 may be in electrical communication witheach other. The DVM communication interface 302 may be configured toreceive and send DVM messages, DVM broadcast responses, and preemptiveresponses to DVM messages. The DVM communication interface 302 maycommunicatively connect the DVM message interceptor 300 with othercomponents of the computing device, including components of a DVMsystem, as described further herein with reference to FIG. 4.

The preemption identifier 304 may be configured to identify DVM messagesthat the DVM message interceptor 300 may terminate and to generate apreemptive responses to the DVM messages. The preemption identifier 304may be configured to implement various techniques and response criteriato identify DVM messages permitted to proceed to the DVM destination, toidentify DVM messages that are terminated, and/or to prompt the DVMmessage interceptor 300 to generate preemptive responses. The DVMmessage 300 interceptors may intercept broadcast DVM messages, and readdestination and/or aspect data of the DVM messages used for determiningwhether the data triggers identification of the DVM messages forforwarding or terminating. The destination and/or aspect data of the DVMmessages may also be used to generate the suitable response forpreemptively responding to DVM messages that are terminated. The DVMmessage interceptor 300 and the preemption identifier 304 may besoftware programmable or a fixed configuration.

The various techniques and criteria that the preemption identifier 304may be configured to implement for identifying broadcast DVM messagesfor termination and/or preemptive response may includewhite-list/black-list identification implementing look-up tables, andmask/match structure identification. The preemption identifier 304 maybe configured for accuracy, performance, or a balance of accuracy andperformance. White-list/black-list identification may be used for higheraccuracy, and mask/match structure identification may be used forimproved performance (speed and/or power usage) relative to each other.

White-list/black-list identification may use data obtained from thereceived broadcast DVM message to compare with data regarding the DVMdestinations or sources downstream from the DVM message interceptor 300.In some aspects, the data of the DVM message may be read and compared todata in one or more lookup tables that contain either or both of awhite-list containing data for matching with data of the DVM messagethat indicate to forward the DVM message, and a black-list containingdata for matching with data of the DVM message that indicate toterminate the DVM message.

In some aspects, the data of the DVM message may be read and analyzedthrough mask/match structure identification. In such aspect, a maskrelating to certain data of the DVM destinations/sources downstream fromthe DVM message interceptor 300 may be compared to the same type of dataobtained from the DVM message to determine whether to forward the DVMmessage or to terminate and/or preemptively respond to the DVM message.

The preemption identifier 304 may be configured to implement any of thefollowing techniques and criteria for white-list/black-listidentification and mask/match structure identification.

Global identification may be used to terminate and/or preemptivelyrespond to all DVM messages the DVM message interceptor 300 receives.Termination of all DVM messages may prevent the receipt of any DVMmessage by an associated DVM source or destination.

Virtual memory identifier (VMID) identification may be used to terminateand/or preemptively respond to all DVM messages without an approved VMID(e.g., white-list) or with an unapproved VMID (e.g., black-list).Termination of a DVM message without an approved VMID or with anunapproved VMID may prevent distribution of the broadcast DVM message toDVM destinations and sources associated with the DVM message interceptor300 other than an intended recipient having a specified VMID.

Shared process context (ASID) identification may terminate and/orpreemptively respond to all DVM messages without an approved ASID (e.g.,white-list) or with an unapproved ASID (e.g., black-list). Terminationof a DVM message without an approved ASID or with an unapproved ASID mayprevent distribution of the broadcast DVM message to DVM destinationsand sources associated with the DVM message interceptor 300 other than arecipient storing or using process context used by the broadcasting DVMsource.

System memory management unit (SMMU) identification may terminate and/orpreemptively respond to DVM messages for specific DVM operations.Termination of a DVM message for a specific DVM operation may preventdistribution of the broadcast DVM message to DVM destinations andsources associated with the DVM message interceptor 300 that may nothandle or may ignore the DVM operation. For example, the DVMdestinations may ignore instruction cache invalidate, branch predictorinvalidate, and the hint operations, and the preemption identifier 304may identify DVM messages for these DVM operations and terminate the DVMmessages for downstream DVM destinations. The DVM destinations mayimplement translation lookaside buffer (TLB) invalidate and synchronizeoperations, and the preemption identifier 304 may identify DVM messagesfor these DVM operations and allow the DVM messages to be forwarded todownstream DVM destinations.

Synchronization identification may terminate and/or preemptively respondto DVM messages for unnecessary synchronization operations. Terminationof unnecessary synchronization operations may prevent receipt of the DVMmessages for synchronization operations if no TLB invalidate operationhas been sent downstream after the last synchronization operation.

Stage identification may terminate and/or preemptively respond to DVMmessages not targeting (e.g., white-list) or targeting (e.g.,black-list) a memory translation stage (e.g., stage 1 or 2). Terminationof DVM messages not targeting or targeting a memory translation stagemay prevent receipt of the DVM messages targeting a memory translationstage other than an allowable memory translation stage.

Execution level (EL) identification may terminate and/or preemptivelyrespond to DVM messages not targeting (e.g., white-list) or targeting(e.g., black-list) an execution level (e.g., Guest OS, Hypervisor, EL3).Termination of DVM messages not targeting or targeting an executionlevel may prevent receipt of the DVM messages targeting an executionlevel other than an allowable execution level.

In various aspects, multiple techniques and criteria may be used incombination to identify broadcast DVM messages to terminate and/orpreemptively acknowledge. For example, SMMU identification of TLBinvalidate operations may be implemented together with synchronizationidentification. As discussed further herein, a DVM message tracker 306may track the status of broadcast DVM messages in relation to a next DVMnode, which may include any of various downstream components of a DVMsystem, as described further herein with reference to FIG. 4, dependingon the location of the DVM message interceptor 300. In some aspects, theDVM message tracker 306 may store the DVM operation of a broadcast DVMmessage, at least until a broadcast DVM message specifyingsynchronization operation is received. The preemption identifier 304 mayuse the information of the DVM message tracker 306 to determine whethera TLB invalidate operation has been issued since the lastsynchronization operation. In response to determining that no TLBinvalidate operation has been issued since the last synchronizationoperation, the preemption identifier 304 may terminate and/orpreemptively respond to a received broadcast DVM message specifying asynchronization operation.

In various aspects, the preemption identifier 304 may be configured withone or a combination of the identification techniques and criteria. Invarious aspects, the preemption identifier 304 may terminate and/orpreemptively respond to a broadcast DVM message for the next DVM nodedownstream of the DVM message interceptor 300 according to thetechniques and criteria with which the preemption identifier 304 isconfigured. In various aspects, for either or both DVM messages that areterminated and that are not terminated, the preemption identifier 304may signal other components of the DVM message interceptor 300,including the DVM message tracker 306 and the DVM message responsegenerator 308. The preemption identifier 304 may send a signal to theDVM message tracker 306 in response to terminating none, some, or all ofthe DVM messages for DVM destinations and sources downstream of the DVMmessage interceptor 300 indicating a state of the DVM message for eachof the DVM destinations and sources. The preemption identifier 304 maysend a signal to the DVM message response generator 306 in response toterminating a DVM message for all of the DVM destinations and sourcesdownstream from the DVM message interceptor 300 indicating a ready statefor sending a response message to the DVM message.

Either in response to receiving the signal from the preemptionidentifier 304 indicating termination or nontermination of a DVMmessage, or upon detecting termination or nontermination of the DVMmessage, the DVM message tracker 306 may update or store data indicatinga status of the DVM message for the DVM destinations and sourcesdownstream from the DVM message interceptor 300. The DVM message tracker306 may correlate a status of each DVM message not yet responded to withthe next DVM node associated with each DVM destination and sourcedownstream from the DVM message interceptor 300.

The preemption identifier 304 or the DVM message tracker 306 may signalthe DVM message interceptor 300 to forward (or not terminate)non-terminated DVM messages to the next DVM node associated with the DVMdestinations and sources downstream from the DVM message interceptor 300for which the DVM messages persist. The DVM message tracker 306 maytrack the status of the forwarded DVM messages, and update the status ofthe DVM message for each DVM destination and source downstream from theDVM message interceptor 300 in response to receiving a response messageto the DVM message from the next DVM node associated with each DVMdestination and source.

In response to receiving a response message, the DVM message tracker 306may send a signal the DVM message response generator 308 indicating aready state for sending a response message to the DVM message. Invarious aspects, the response message to the DVM message for each DVMdestination and source may include an individual response message fromone or more of the DVM destinations and sources, or a cumulativeresponse message from a downstream DVM message interceptor 300, or a DVMcoherent interconnect or DVM network component (not shown). In variousaspects, for DVM messages that are terminated for all DVM destinationsand sources downstream from the DVM message interceptor 300, the DVMmessage tracker 306 may send a signal to the DVM message responsegenerator 308, instead of the signal sent from the preemption identifier304 to the DVM message response generator 308 indicating a ready statefor sending a response message to the DVM message.

In response to receiving the signal from the preemption identifier 304or from the DVM message tracker 306 indicating a ready state for sendinga response message to the DVM message, or upon detecting termination ofthe DVM message for all the DVM destinations and sources downstream fromthe DVM message interceptor 300, the DVM message response generator 308may generate a DVM message response. The DVM message response may be astandard DVM message response or a preemptive DVM message response. TheDVM message interceptor 300 may send the standard DVM message responsesand the preemptive DVM message responses to a component of the computingdevice upstream of the DVM message interceptor 300.

A standard DVM message response may be generated in response toreceiving the signal from the DVM message tracker 306 after receiving aresponse message to the DVM message for all of the DVM destination andsource downstream from the DVM message interceptor 300. The standard DVMmessage response may be a cumulative DVM message response representingmessage responses for all of the DVM destination and source downstreamfrom the DVM message interceptor 300.

A preemptive DVM message response may be generated after termination ofthe DVM message for all the DVM destinations and sources downstream fromthe DVM message interceptor 300 by the preemption identifier 304. Thepreemptive DVM message response may be a cumulative DVM message responserepresenting message responses for all of the DVM destination and sourcedownstream from the DVM message interceptor 300.

FIG. 4 illustrates an example DVM system 400 with DVM messageinterceptors 300 a-300 i suitable for implementing some aspects. The DVMsystem may include any number of DVM sources 402 a, 402 b, a DVMcoherent interconnect 414, one or more DVM networks 416, and any numberof DVM destinations 412 a-412 d. The DVM coherent interconnect 414 mayinclude an aggregator 404, a serializer 406, any number of broadcasters410 a, 410 b, and any number of DVM message interceptors 300 a-300 f.

The DVM network 416 may include any number of broadcasters 410 c and anynumber of DVM message interceptors 300 g-300 i. The DVM sources 402 a,402 b may include any processing device or hardware core as describedherein, such as the processor 14 described with reference to FIGS. 1 and2. The of DVM destinations 412 a-412 d may include memory managementunits, such as system memory management units, configured to controlaccess to and implement functions for memory devices, such as the memory16 described with reference to FIG. 1.

The DVM sources 402 a, 402 b may be configured to broadcast DVM messageshaving various data for implementing DVM operations, including variouscombinations of a type of DVM operation (or opcode that may includetranslation lookaside buffer invalidate (TLBI), synchronization (SYNC),L1I invalidation, hint, etc.), an attached or associated VMID for anintended recipient DVM sources 402 a, 402 b or DVM destinations 412a-412 d, an attached or associated ASID for the execution of the DVMoperation, a memory translation stage for the execution of the DVMoperations, and an execution level for the execution of the DVMoperations. The DVM sources 402 a, 402 b may also receive standard DVMmessage responses and preemptive DVM message responses. The DVM sources402 a, 402 b may broadcast the DVM messages to other DVM sources 402 a,402 b and/or to DVM destinations 412 a-412 d via the DVM coherentinterconnect 414 and the one or more DVM networks 416. The DVM sources402 a, 402 b may also receive standard DVM message responses andpreemptive DVM message responses via the DVM coherent interconnect 414and the one or more DVM networks 416 in response to a sent DVM message.

The DVM coherent interconnect 414 may be configured to receive andbroadcast the DVM messages from the DVM sources 402 a, 402 b, toreceive, from the DVM sources 402 a, 402 b and the DVM destinations 412a-412 d, the standard DVM message responses and preemptive DVM messageresponses, and to send the DVM message responses to the DVM sources 402a, 402 b that sent the DVM messages.

The aggregator 404 may be configured to receive the DVM messages fromthe sending DVM sources 402 a, 402 b, send the DVM messages to theserializer 406, receive the DVM responses from the serializer 406, andsend the DVM responses to the sending DVM sources 402 a, 402 b.

The DVM serializer 406 may be configured to receive the DVM messagesfrom the aggregator 404, and to convert the DVM messages from a parallelformat to a serial format for sending through the DVM coherentinterconnect 414 and the DVM networks 416. The DVM serializer 406 may beconfigured to receive the DVM messages responses from the broadcaster410 a, and establish a global order among the various coherent mastersof the coherent interconnect 414.

The DVM message interceptors 300 a-300 f may be configured to receivethe DVM messages from the serializer 406, other DVM message interceptors300 a-300 i, and the broadcasters 410 a-410 c, and to forward or enabletransmission of the DVM messages to the other DVM sources 402 a, 402 band the DVM destinations 412 a-412 d, in some aspects via thebroadcasters 410 a-410 c and other DVM message interceptors 300 a-300 i.The DVM message interceptors 300 a-300 f may receive the DVM messageresponses from the other DVM sources 402 a, 402 b and the DVMdestinations 412 a-412 d, in some aspects via the broadcasters 410 a-410c and other DVM message interceptors 300 a-300 i. In various aspects,DVM nodes upstream and downstream from any DVM message interceptor 300a-300 i may include another DVM message interceptor 300 a-300 i and/or abroadcaster 410 a-410 c.

In various aspects, DVM nodes downstream from any DVM messageinterceptor 300 a-300 i may also include a DVM source 402 a, 402 b or aDVM destination 412 a-412 d. DVM nodes including a downstream DVM source402 a, 402 b or DVM destination 412 a-412 d may be identified as a lastlevel DVM node. Any DVM nodes downstream from a DVM message interceptor300 a-300 i, including last level DVM nodes, may be identified as a nextDVM node or next level DVM node.

The DVM message interceptors 300 a-300 f may send a standard DVM messageresponse, representing a DVM message response from each of thedownstream next DVM nodes, to the sending DVM source 410 a, 410 b viathe serializer 406, and in some aspects also via the broadcasters 410a-410 c and other DVM message interceptors 300 a-300 i.

The broadcasters 410 a, 410 b may be configured to receive the DVMmessages from the serializer 406, the DVM message interceptors 300 a-300i, and other broadcasters 410 a-410 c, and to broadcast the DVM messagesto the other DVM sources 402 a, 402 b and the DVM destinations 412 a-412d via other broadcasters 410 a-410 c and other DVM message interceptors300 a-300 i. The broadcasters 410 a, 410 b may be configured receive theDVM response messages from the other broadcasters 410 a-410 c and otherDVM message interceptors 300 a-300 i, and to send the DVM responsemessages to the serializer 406, the DVM message interceptors 300 a-300i, and other broadcasters 410 a-410 c from which the broadcasters 410a-410 c received the DVM messages.

In various aspects, the configuration of the various components of theDVM coherent interconnect 414 may include additional or fewercomponents. In various aspects, whether a DVM message or DVM responsemessage is sent to or received from another component may depend on theconfiguration of the DVM coherent interconnect 414. For example, thebroadcaster 410 b a may receive a DVM message directly from theserializer 406, directly from the DVM message interceptor 300 a or 300b, or directly from the broadcaster 410 a depending on which of thecomponents are implemented in the DVM coherent interconnect 414.

The one or more DVM networks 416 may be configured to receive andbroadcast the DVM messages from the DVM sources 402 a, 402 b via the DVMcoherent interconnect 414, and to receive the standard DVM messageresponses and preemptive DVM message responses from the DVM sources 402a, 402 b and the DVM destinations 412 a-412 d. The one or more DVMnetworks 416 may be configured to send the DVM message responses to theDVM sources 402 a, 402 b that sent the DVM messages via the DVM coherentinterconnect 414. The broadcaster 410 c and the DVM message interceptors300 g-300 i may be configured in a similar manner to the broadcasters410 a and 410 b, and the DVM message interceptors 300 a-300 f,respectively, as described herein with respect to the DVM coherentinterconnect 414.

In various aspects, the configuration of the various components of theone or more DVM networks 416 may include additional or fewer components.In various aspects, whether a DVM message or DVM response message issent to or received from another component may depend on theconfiguration of the one or more DVM networks 416.

The DVM sources 410 a, 410 b and the DVM destinations 412 a-412 d may beconfigured to receive the DVM messages via the DVM coherent interconnect414 and the one or more DVM networks 416. The DVM sources 410 a, 410 band the DVM destinations 412 a-412 d may be configured to respond toreceiving the DVM messages by implementing a DVM operation and sending aDVM response message, ignoring the DVM message, or responding to the DVMmessage with a DVM response message without implementing the DVMoperation.

FIGS. 5A and 5B illustrate examples of signaling involved in distributedvirtual memory preemptive responding according to various aspects.

Referring to FIG. 5A, a DVM source 402 a may issue a DVM message 504.Components of the DVM coherent interconnect 500, including one or moreof the aggregator 404, the serializer 406, and the broadcasters 410 a,410 b for the DVM coherent interconnect 414 described with reference toFIG. 4, may receive the DVM message. Depending on the components of theDVM coherent interconnect 500 receiving the DVM message, operations maybe implemented to serialize or broadcast the DVM message.

The components of the DVM coherent interconnect 500 may send the DVMmessage 506, and the DVM message may be received by a DVM messageinterceptor 300, as described herein with reference to FIGS. 3 and 4.The DVM message interceptor 300 may be configured to analyze data of theDVM message 508 to identify whether to forward the DVM message or torespond to the DVM message with a preemptive DVM response. In theexample illustrated in FIG. 5A, the DVM message interceptor 300determines that the DVM message 510 should be delivered (e.g., forwardedor allowed to continue) to the DVM destination(s) and/or source(s)downstream of the DVM message interceptor 300. Components of the DVMnetwork 502, including the broadcaster 410 c and the DVM messageinterceptors 300 g-300 i, as described herein with reference to FIG. 4,may receive the forwarded DVM message. Depending on the components ofthe DVM network 502 receiving the DVM message, operations may beimplemented to broadcast or analyze the data of the DVM message. Thecomponents of the DVM network 502 may forward the DVM message 512 a, 512b, 512 c to one or more DVM destinations 412 a, 412 d and DVM source 402b.

A DVM destination 412 a, 412 d or DVM source 402 b (e.g., describedherein with reference to FIG. 4) may receive the forwarded DVM message512 a, 512 b, 512 c. In some aspects, the DVM destination 412 a, 412 dor DVM source 402 b may implement a DVM operation designated by the DVMmessage, and generate and send back a DVM response message 514 a, 514 b,514 c. In some aspects, the DVM destination 412 a, 412 b may ignore theDVM message and send back the DVM response message 514 a, 514 b. The DVMnetwork components 502, including the broadcaster, may receive the DVMresponse messages 514 a, 514 b, 514 c, aggregate or merge the DVMresponse messages 514 a, 514 b, 514 c, and send a DVM response message516 for one or more DVM destinations 412 a, 412 b or DVM sources 402 b.In aspects forwarding multiple DVM messages 512 a, 512 b, 514 c, to oneor more DVM destinations 412 a, 412 d or DVM sources 402 b, the DVMnetwork components 502 may wait until receiving all the DVM responsemessages 514 a, 514 b, 514 c before sending the DVM response message516.

In some aspects, the DVM response message may be a standard DVM responsemessage generated by a DVM message interceptor 300 g-300 i. In someaspects, rather than the DVM network components 502 receiving theforwarded DVM message, the forwarded DVM message may be receiveddirectly by the issuing DVM destination 402 a. The DVM destination maysend the DVM response message directly to the DVM message interceptor300.

The DVM message interceptor 300 may generate and send a standard DVMmessage response 518, representing a DVM message response 514 a, 514 b,514 c from each of the downstream DVM sources 402 b and DVM destinations412 a, 412 d, for example aggregated DVM response 516. The DVM messageinterceptor 300 may generate the standard DVM message response inresponse 518 to receiving the DVM response message 514 a, 514 b, 514 c.The DVM coherent interconnect components 500 may receive the standardDVM message response 518. In some aspects, the DVM coherent interconnectcomponents 500 may forward the standard DVM message response 520 to theissuing DVM source 402 a.

In the example illustrated in FIG. 5B, the DVM message interceptor 300determines that a preemptive DVM response message should be generated inresponse to the DVM message 506, and sends the preemptive responsemessage 522. The determination made to generate and send the preemptiveDVM response message may be based on the identification techniques andcriteria as described herein with reference to FIG. 3. The DVM coherentinterconnect components 500 may receive the preemptive DVM responsemessage, and forward the preemptive DVM response message 524 to theissuing DVM source 402 a.

FIG. 6 illustrates an example method 600 for implementing DVM preemptiveresponding according to various aspects. The method 600 may beimplemented in a DVM interceptor (e.g., the DVM message interceptor 300in FIGS. 3, 4, 5A, and 5B) which may be implemented in a processorexecuting software implementing the method 600, in general purposehardware/circuitry, in dedicated hardware/circuitry, or in a combinationof a processor and dedicated hardware. In order to encompass thealternative configurations enabled in the various aspects, the hardwareimplementing the method 600 is referred to herein as a “DVMinterceptor.”

In block 602, the DVM interceptor may receive a broadcast DVM message.In determination block 604, the DVM interceptor may determine whether tobroadcast the DVM message to the next level of DVM nodes. Next level DVMnodes may include other DVM interceptors, DVM network components, suchas broadcasters, DVM destinations, and DVM sources depending on thelocation of the DVM interceptor. As described herein with reference toFIG. 3, the DVM interceptor may use one or more techniques and criteriain identifying broadcast DVM messages to broadcast to the next level ofDVM nodes or to respond to with a preemptive DVM message response. Invarious aspects, determining whether to broadcast the broadcast DVMmessage or generate and sent a preemptive DVM message response maydepend on data of the broadcast DVM response compared withwhite-list/black-list data or mask/match structure identificationanalysis. The bases for the comparison or analysis may include any oneor combination of broadcast DVM message, VMID, ASID, specific DVMoperations, synchronization operations, target translation stages, andtarget execution level stages. The determination of whether to broadcastthe broadcast DVM message or to generate and send a preemptive DVMmessage response may be made for each DVM destination or sourcedownstream from the component of the DVM interceptor making thedetermination.

In response to determining not to broadcast the broadcast DVM message tothe next level of DVM nodes (i.e., determination block 604=“No”), theDVM interceptor may generate a preemptive DVM message response messagein block 606. The preemptive DVM response message may represent aresponse for all of the DVM destinations and sources downstream from thecomponent of the DVM interceptor making the determination. In block 608,the DVM interceptor may send the preemptive DVM message response to acomponent of the DVM system upstream of the component of the DVMinterceptor making the determination, including a previous level DVMnode.

In response to determining that to the broadcast DVM message should bebroadcast to the next level of DVM nodes (i.e., determination block604=“Yes”), the DVM interceptor may forward (or enable transmission of)the broadcast DVM message to the next level DVM nodes downstream fromthe component of the DVM interceptor making the determination in block610. As described herein, the determination of whether to broadcast thebroadcast DVM message or to generate and send a preemptive DVM messageresponse to the broadcast DVM message may be made for each DVMdestination or source downstream from the component of the DVMinterceptor making the determination. Therefore, the DVM interceptor mayforward the broadcast DVM message to the next level DVM nodes downstreamfrom the component of the DVM interceptor making the determinationdepending on the determination for each DVM destination or source. Invarious aspects, a determination to broadcast the broadcast DVM messageto a single downstream DVM destination or source may trigger thedetermination to broadcast the broadcast DVM message to some or all ofthe next level DVM nodes.

In block 612, the DVM interceptor may receive a standard DVM messageresponse or a preemptive DVM message response. The standard DVM messageresponse or a preemptive DVM message response may be received from anext level DVM node, including a DVM destination or source, a DVMmessage interceptor, or a broadcaster, downstream from the component ofthe DVM interceptor making the determination.

In determination block 614, the DVM interceptor may determine whetherall DVM message responses are received from the next level DVM nodes orfinal destinations, last level DVM nodes, downstream from the componentof the DVM interceptor making the determination. As described herein,the standard DVM message response and the preemptive DVM messageresponse may be cumulative DVM message responses for multiple downstreamDVM destinations or sources sent by and received from a next level DVMnode. Therefore, receiving a single standard DVM message response and apreemptive DVM message response may represent receiving a response forone or more downstream DVM destinations or sources. In various aspects,a standard DVM message response or a preemptive DVM message responserepresenting multiple downstream DVM destinations or sources mayoriginate from a next level DVM node, including a DVM messageinterceptor or a broadcaster. In various aspects, a standard DVM messageresponse representing a single downstream DVM destination or source mayoriginate from a next level DVM node or last level DVM node, includingthe downstream DVM destination or source. The DVM interceptor may trackthe status of the broadcast DVM message in relation to each next levelDVM node downstream from the component of the DVM interceptor making thedetermination, and use the tracking data to determine, in determinationblock 614, whether the status of the broadcast DVM message indicatesthat the response DVM message is received from any next level DVM nodedownstream from the component of the DVM interceptor making thedetermination.

In response to determining that not all DVM message responses arereceived for all DVM destinations or source downstream from thecomponent of the DVM interceptor making the determination (i.e.,determination block 614=“No”), the DVM interceptor may receive morestandard DVM message responses or preemptive DVM message responses inblock 612.

In response to determining that all DVM message responses are receivedfor all DVM destinations or source downstream from the component of theDVM interceptor making the determination (i.e., determination block614=“Yes”), the DVM interceptor may generate a standard DVM messageresponse in block 616. The generated standard DVM message response mayrepresent a DVM message response for all DVM destinations or sourcedownstream from the component of the DVM interceptor making thedetermination.

In block 618, the DVM interceptor may send the standard DVM messageresponse to a component of the DVM system upstream of the component ofthe DVM interceptor making the determination.

The various aspects (including, but not limited to, aspects describedabove with reference to FIGS. 1-6) may be implemented in a wide varietyof computing systems including mobile computing devices, an example ofwhich suitable for use with the various aspects is illustrated in FIG.7. The mobile computing device 700 may include a processor 702 coupledto a touchscreen controller 704 and an internal memory 706. Theprocessor 702 may be one or more multicore integrated circuitsdesignated for general or specific processing tasks. The internal memory706 may be volatile or non-volatile memory, and may also be secureand/or encrypted memory, or unsecure and/or unencrypted memory, or anycombination thereof. Examples of memory types that can be leveragedinclude but are not limited to DDR, LPDDR, GDDR, WIDEIO, RAM, SRAM,DRAM, P-RAM, R-RAM, M-RAM, STT-RAM, and embedded DRAM.

The touchscreen controller 704 and the processor 702 may also be coupledto a touchscreen panel 712, such as a resistive-sensing touchscreen,capacitive-sensing touchscreen, infrared sensing touchscreen, etc.Additionally, the display of the computing device 700 need not havetouch screen capability.

The mobile computing device 700 may have one or more radio signaltransceivers 708 (e.g., Peanut, Bluetooth, Zigbee, Wi-Fi, RF radio) andantennae 710, for sending and receiving communications, coupled to eachother and/or to the processor 702. The transceivers 708 and antennae 710may be used with the above-mentioned circuitry to implement the variouswireless transmission protocol stacks and interfaces. The mobilecomputing device 700 may include a cellular network wireless modem chip716 that enables communication via a cellular network and is coupled tothe processor.

The mobile computing device 700 may include a peripheral deviceconnection interface 718 coupled to the processor 702. The peripheraldevice connection interface 718 may be singularly configured to acceptone type of connection, or may be configured to accept various types ofphysical and communication connections, common or proprietary, such asUniversal Serial Bus (USB), FireWire, Thunderbolt, or PCIe. Theperipheral device connection interface 718 may also be coupled to asimilarly configured peripheral device connection port (not shown).

The mobile computing device 700 may also include speakers 714 forproviding audio outputs. The mobile computing device 700 may alsoinclude a housing 720, constructed of a plastic, metal, or a combinationof materials, for containing all or some of the components describedherein. The mobile computing device 700 may include a power source 722coupled to the processor 702, such as a disposable or rechargeablebattery. The rechargeable battery may also be coupled to the peripheraldevice connection port to receive a charging current from a sourceexternal to the mobile computing device 700. The mobile computing device700 may also include a physical button 724 for receiving user inputs.The mobile computing device 700 may also include a power button 726 forturning the mobile computing device 700 on and off.

The various aspects (including, but not limited to, aspects describedabove with reference to FIGS. 1-6) may be implemented in a wide varietyof computing systems include a laptop computer 800 an example of whichis illustrated in FIG. 8. Many laptop computers include a touchpad touchsurface 817 that serves as the computer's pointing device, and thus mayreceive drag, scroll, and flick gestures similar to those implemented oncomputing devices equipped with a touch screen display and describedabove. A laptop computer 800 will typically include a processor 811coupled to volatile memory 812 and a large capacity nonvolatile memory,such as a disk drive 813 of Flash memory. Additionally, the computer 800may have one or more antenna 808 for sending and receivingelectromagnetic radiation that may be connected to a wireless data linkand/or cellular telephone transceiver 816 coupled to the processor 811.The computer 800 may also include a floppy disc drive 814 and a compactdisc (CD) drive 815 coupled to the processor 811. In a notebookconfiguration, the computer housing includes the touchpad 817, thekeyboard 818, and the display 819 all coupled to the processor 811.Other configurations of the computing device may include a computermouse or trackball coupled to the processor (e.g., via a USB input) asare well known, which may also be used in conjunction with the variousaspects.

The various aspects (including, but not limited to, aspects describedabove with reference to FIGS. 1-6) may also be implemented in fixedcomputing systems, such as any of a variety of commercially availableservers. An example server 900 is illustrated in FIG. 9. Such a server900 typically includes one or more multi-core processor assemblies 901coupled to volatile memory 902 and a large capacity nonvolatile memory,such as a disk drive 904. As illustrated in FIG. 9, multi-core processorassemblies 901 may be added to the server 900 by inserting them into theracks of the assembly. The server 900 may also include a floppy discdrive, compact disc (CD) or digital versatile disc (DVD) disc drive 906coupled to the processor 901. The server 900 may also include networkaccess ports 903 coupled to the multi-core processor assemblies 901 forestablishing network interface connections with a network 905, such as alocal area network coupled to other broadcast system computers andservers, the Internet, the public switched telephone network, and/or acellular data network (e.g., CDMA, TDMA, GSM, PCS, 3G, 4G, LTE, or anyother type of cellular data network).

Computer program code or “program code” for execution on a programmableprocessor for carrying out operations of the various aspects may bewritten in a high level programming language such as C, C++, C#,Smalltalk, Java, JavaScript, Visual Basic, a Structured Query Language(e.g., Transact-SQL), Perl, or in various other programming languages.Program code or programs stored on a computer readable storage medium asused in this application may refer to machine language code (such asobject code) whose format is understandable by a processor.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the operations of the various aspects must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of operations in the foregoing aspects may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the operations; these words are simply used toguide the reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm operations described in connection with the various aspectsmay be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and operations have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such aspect decisions should not beinterpreted as causing a departure from the scope of the claims.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with the aspectsdisclosed herein may be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Alternatively, some operations ormethods may be performed by circuitry that is specific to a givenfunction.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored as one or more instructions orcode on a non-transitory computer-readable medium or a non-transitoryprocessor-readable medium. The operations of a method or algorithmdisclosed herein may be embodied in a processor-executable softwaremodule that may reside on a non-transitory computer-readable orprocessor-readable storage medium. Non-transitory computer-readable orprocessor-readable storage media may be any storage media that may beaccessed by a computer or a processor. By way of example but notlimitation, such non-transitory computer-readable or processor-readablemedia may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to store desired programcode in the form of instructions or data structures and that may beaccessed by a computer. Disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk, and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofnon-transitory computer-readable and processor-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed aspects is provided to enableany person skilled in the art to make or use the claims. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects and aspects without departing from the scope of theclaims. Thus, the present disclosure is not intended to be limited tothe aspects and aspects described herein, but is to be accorded thewidest scope consistent with the following claims and the principles andnovel features disclosed herein.

What is claimed is:
 1. A method of distributive virtual memory (DVM)preemptive responding on a computing device, comprising: receiving a DVMmessage broadcast from a first DVM source in a DVM message interceptorprior to delivery of the DVM message to a DVM destination; determiningbased on a content of the DVM message whether a preemptive DVM messageresponse should be sent by the DVM message interceptor; generating thepreemptive DVM message in response to determining that a preemptive DVMmessage response should be sent by the DVM message interceptor; andsending the preemptive DVM message response from the DVM messageinterceptor to the first DVM source.
 2. The method of claim 1, furthercomprising enabling the broadcast DVM message to reach the DVMdestination in response to determining that a preemptive DVM messageresponse should not be sent by the DVM message interceptor.
 3. Themethod of claim 1, wherein the DVM destination is a memory managementunit and the DVM message interceptor is positioned within a DVM systemto intercept the DVM message before the DVM message reaches the memorymanagement unit.
 4. The method of claim 1, further comprising preventingthe DVM destination from receiving the broadcast DVM message in responseto determining that a preemptive DVM message response should be sent bythe DVM message interceptor.
 5. The method of claim 1, whereindetermining based on a content of the DVM message whether a preemptiveDVM message response should be sent by the DVM message interceptorcomprises: comparing data obtained from the broadcast DVM message withcorresponding data in at least one of a white-list and a black-list; anddetermining whether a preemptive DVM message response should be sent bythe DVM message interceptor based upon the comparison.
 6. The method ofclaim 1, wherein determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent by the DVMmessage interceptor comprises applying a mask to data obtained from thebroadcast DVM message.
 7. The method of claim 1, wherein determiningbased on a content of the DVM message whether a preemptive DVM messageresponse should be sent by the DVM message interceptor comprisescomparing data obtained from the broadcast DVM message with a criterioncomprising at least one of a virtual memory identifier, a shared processcontext, a DVM operation, a memory translation stage identifier, and anexecution level identifier.
 8. A distributive virtual memory (DVM)message interceptor, comprising: a DVM communication interface; apreemption identifier communicatively connected to the DVM communicationinterface; and a DVM message response generator communicativelyconnected to the DVM communication interface and the preemptionidentifier, wherein: the DVM communication interface is configured toperform operations comprising: receiving a DVM message broadcast from afirst DVM source prior to delivery of the DVM message to a DVMdestination; and sending a preemptive DVM message response to the firstDVM source; the preemption identifier is configured to performoperations comprising determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent; and the DVMmessage response generator is configured to perform operationscomprising generating the preemptive DVM message in response todetermining that a preemptive DVM message response should be sent. 9.The DVM message interceptor of claim 8, wherein the DVM communicationinterface is configured to perform operations further comprisingenabling the broadcast DVM message to reach the DVM destination inresponse to determining that a preemptive DVM message response shouldnot be sent.
 10. The DVM message interceptor of claim 8, wherein the DVMdestination is a memory management unit and the DVM message interceptoris positioned within a DVM system downstream from a DVM source issuingthe DVM message and upstream from the memory management unit tointercept the DVM message before the DVM message reaches the memorymanagement unit.
 11. The DVM message interceptor of claim 8, wherein thepreemption identifier is configured to perform operations furthercomprising preventing the DVM destination from receiving the broadcastDVM message in response to determining that a preemptive DVM messageresponse should be sent.
 12. The DVM message interceptor of claim 8,wherein the preemption identifier is configured to perform operationssuch that determining based on a content of the DVM message whether apreemptive DVM message response should be sent comprises: comparing dataobtained from the broadcast DVM message with corresponding data in atleast one of a white-list and a black-list; and determining whether apreemptive DVM message response should be sent based upon thecomparison.
 13. The DVM message interceptor of claim 8, wherein thepreemption identifier is configured to perform operations such thatdetermining based on a content of the DVM message whether a preemptiveDVM message response should be sent comprises applying a mask to dataobtained from the broadcast DVM message.
 14. The DVM message interceptorof claim 8, wherein the preemption identifier is configured to performoperations such that determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent comprisescomparing data obtained from the broadcast DVM message with a criterioncomprising at least one of a virtual memory identifier, a shared processcontext, a DVM operation, a memory translation stage identifier, and anexecution level identifier.
 15. A distributive virtual memory (DVM)message interceptor, comprising: means for receiving a DVM messagebroadcast from a first DVM source in a DVM message interceptor prior todelivery of the DVM message to a DVM destination; means for determiningbased on a content of the DVM message whether a preemptive DVM messageresponse should be sent; means for generating the preemptive DVM messagein response to determining that a preemptive DVM message response shouldbe sent; and means for sending the preemptive DVM message response tothe first DVM source.
 16. The DVM message interceptor of claim 15,further comprising means for enabling the broadcast DVM message to reachthe DVM destination in response to determining that a preemptive DVMmessage response should not be sent.
 17. The DVM message interceptor ofclaim 15, wherein the DVM destination is a memory management unit andthe DVM message interceptor further comprising means to intercept theDVM message before the DVM message reaches the memory management unit.18. The DVM message interceptor of claim 15, further comprising meansfor preventing the DVM destination from receiving the broadcast DVMmessage in response to determining that a preemptive DVM messageresponse should be sent.
 19. The DVM message interceptor of claim 15,wherein means for determining based on a content of the DVM messagewhether a preemptive DVM message response should be sent comprises:means for comparing data obtained from the broadcast DVM message withcorresponding data in at least one of a white-list and a black-list; andmeans for determining whether a preemptive DVM message response shouldbe sent based upon the comparison.
 20. The DVM message interceptor ofclaim 15, wherein means for determining based on a content of the DVMmessage whether a preemptive DVM message response should be sentcomprises means for applying a mask to data obtained from the broadcastDVM message.
 21. The DVM message interceptor of claim 15, wherein meansfor determining based on a content of the DVM message whether apreemptive DVM message response should be sent comprises means forcomparing data obtained from the broadcast DVM message with a criterioncomprising at least one of a virtual memory identifier, a shared processcontext, a DVM operation, a memory translation stage identifier, and anexecution level identifier.
 22. A non-transitory processor-readablestorage medium having stored thereon processor-executable instructionsconfigured to cause a processor of a distributive virtual memory (DVM)message interceptor to perform operations comprising: receiving a DVMmessage broadcast from a first DVM source in a DVM message interceptorprior to delivery of the DVM message to a DVM destination; determiningbased on a content of the DVM message whether a preemptive DVM messageresponse should be sent; generating the preemptive DVM message inresponse to determining that a preemptive DVM message response should besent; and sending the preemptive DVM message response to the first DVMsource.
 23. The non-transitory processor-readable storage medium ofclaim 22, wherein the stored processor-executable instructions areconfigured to cause the processor to perform operations furthercomprising enabling the broadcast DVM message to reach the DVMdestination in response to determining that a preemptive DVM messageresponse should not be sent.
 24. The non-transitory processor-readablestorage medium of claim 22, wherein the DVM destination is a memorymanagement unit and wherein the stored processor-executable instructionsare configured to intercept the DVM message before the DVM messagereaches the memory management unit.
 25. The non-transitoryprocessor-readable storage medium of claim 22, wherein the storedprocessor-executable instructions are configured to cause the processorto perform operations further comprising preventing the DVM destinationfrom receiving the broadcast DVM message in response to determining thata preemptive DVM message response should be sent.
 26. The non-transitoryprocessor-readable storage medium of claim 22, wherein the storedprocessor-executable instructions are configured to cause the processorto perform operations such that determining based on a content of theDVM message whether a preemptive DVM message response should be sentcomprises: comparing data obtained from the broadcast DVM message withcorresponding data in at least one of a white-list and a black-list; anddetermining whether a preemptive DVM message response should be sentbased upon the comparison.
 27. The non-transitory processor-readablestorage medium of claim 22, wherein the stored processor-executableinstructions are configured to cause the processor to perform operationssuch that determining based on a content of the DVM message whether apreemptive DVM message response should be sent comprises applying a maskto data obtained from the broadcast DVM message.
 28. The non-transitoryprocessor-readable storage medium of claim 22, wherein the storedprocessor-executable instructions are configured to cause the processorto perform operations such that determining based on a content of theDVM message whether a preemptive DVM message response should be sentcomprises comparing data obtained from the broadcast DVM message with acriterion comprising at least one of a virtual memory identifier, ashared process context, a DVM operation, a memory translation stageidentifier, and an execution level identifier.